Networking cooperation method and machine using such method

ABSTRACT

A networking cooperation method and a machine using the method are provided. The networking cooperation method includes the following steps. Firstly, plural unified matters are combined together into a projectable space instance for modeling a relational synchronization workspace according to an operational demand. Then, the relational synchronization workspace is projected to multiple cooperators. The projected relational synchronization workspace equips the plural unified matters according to the projectable space instance. When the projected relational synchronization workspace is accessed by at least one cooperator, the at least one cooperator and at least one other cooperator will cooperatively implement a task. Any information, any tool or any service can be arbitrarily combined together into the cooperative working environment by any cooperator according to the practical requirements. Moreover, any cooperator can operate any content of the cooperative working environment.

TECHNICAL FIELD

The present invention relates to a networking cooperation method, andmore particularly to a networking cooperation method for cooperativelyimplementing a task through a relational synchronization workspace and amachine using the method.

BACKGROUND

In today's convenience daily life, people are accustomed to use anelectronic device with computational capability to achieve various kindsof applications. For example, these applications include working, fileprocessing, entertainment, social communication, and so on. Withdevelopment of science and technology, information can be propagatedmore quickly. Accordingly, various web platforms, operating systems andsoftware tools have been have been developed for people to use, andbrought more efficient lives to the users. Especially in the post-PCera, the conventional desktop computers, tablet computers, mobile phonesor other mobile devices still make people to implement tasks wheneverand wherever they are, and people over the world communicate with eachother to transmit and share information through Internet.

Generally, the existing technologies (regardless of hardware orsoftware) are developed in view of personal devices (e.g., computers).That is, a large number of data stations with obvious barriers in thenetworks become obstruction for many people to cooperatively implement atask. Under this circumstance, the purpose of having no internationallimitation in network cannot be successfully achieved. In particular,the cooperation method in the real life should comply with the followingthree conditions: people participation, communication channels, andsynchronization of the displayed content. However, if many cooperatorsare ready to use personal devices (e.g., computers) at different placesto cooperatively implement a task through network connection, it isdifficult to comply with the above three conditions simultaneously.Especially, it is a challenge to comply with the third condition becauseof the network security and privacy. If the personal devices (e.g.,computers) of all cooperators are connected with the personal device(e.g., a computer) of a specified cooperator to view and operate aspecified object (e.g., TeamViewer® remote control software), thenetwork security and privacy are possibly lost.

For solving the above drawbacks, many researches pay much attention tothe development of a working environment for cooperatively implementingthe task through network connection. For example, Skype® internetinstant messaging software provides a medium for communication anddiscussion because of the following features. Firstly, as long as theSkype® internet instant messaging software is installed in a personaldevice (e.g., a computer) of a user, the user can be invited as a memberof a cooperator list in order to cooperatively implement a task withother cooperators. Secondly, the cooperators can communicate and discusswith each other via messages, audio means or video means. Thirdly, thecooperators can share their own screen images to show the content of thetask.

Although the Skype® internet instant messaging software appears to meetthe above three conditions of cooperatively implementing the task, thereare still some drawbacks in practical applications. Firstly, it isnecessary to install the Skype® internet instant messaging software inthe personal devices (e.g., computers) of all cooperators in order tocooperatively implement the task. Secondly, any cooperator cannotconfigure a desired tool (e.g., a video recorder) on the Skype® internetinstant messaging software according to the practical requirements.Thirdly, the way of sharing the own screen image to show the workingcontent has some limitations. For example, the working content shared bythe sharer can be operated by the sharer only, and the other user canonly view the shared working content and make a speech and discuss aboutthe shard working content. In other words, even if the cooperativeworking content is synchronously shown, only one person has the right tooperate the working content. Fourthly, since the display screens of thepersonal devices (e.g., computers) of all cooperators are not alwaysidentical, the screen image shared by the sharer is not sure to becompletely shown on the display screens of the receivers. For example,if the display screen of the sharer is much smaller than the displayscreen of the receiver, the screen image viewed by the receiver isblurred. Fifthly, the approach of sharing the own screen image to showthe working content may occupy a lot of the network bandwidth. Underthis circumstance, the network performance is deteriorated (e.g., audiodelay or video delay).

From the above discussions, the cooperative working environment tocooperatively implement the task should have the following benefits.Firstly, any identity can be invited to join the cooperative workingenvironment to cooperatively implement the task. Secondly, anyinformation, any tool or any service can be arbitrarily combinedtogether into the cooperative working environment by any cooperatoraccording to the practical requirements. Thirdly, any cooperator canaccess any content of the cooperative working environment, and anycooperator can simultaneously view the change of the cooperative workingenvironment in response to an operation of other cooperator.

SUMMARY

For solving the drawbacks of the conventional technologies, the presentinvention provides a networking cooperation method and a machine usingthe method. By the networking cooperation method, any identity can beinvited to join the cooperative working environment to cooperativelyimplement a task. Moreover, any information, any tool or any service canbe arbitrarily combined together into the cooperative workingenvironment by any cooperator according to the practical requirements.Moreover, any cooperator can access any content of the cooperativeworking environment, and any cooperator can simultaneously view thechange of the cooperative working environment in response to anoperation of other cooperator.

In accordance with an aspect of the present invention, there is provideda networking cooperation method. The networking cooperation methodincludes the following steps. Firstly, a plurality of unified mattersare combined together into a projectable space instance for modeling arelational synchronization workspace according to an operational demandfrom at least one promoter. Then, the relational synchronizationworkspace is projected to at least one participant. The projectedrelational synchronization workspace equips the plurality of unifiedmatters according to the projectable space instance. The at least oneparticipant accesses the projected relational synchronization workspaceand cooperatively implement a task with the at least one promoter and/orat least one other participant.

In an embodiment, at least two of the at least one promoter, the atleast one participant and the at least one other participant are relatedwith each other according to the operational demand.

In an embodiment, when at least one of the at least one promoter, the atleast one participant and the other participant performs at least oneoperation on the corresponding projected relational synchronizationworkspace to result in a change of the corresponding projectedrelational synchronization workspace, the projected relationalsynchronization workspace corresponding to at least another of the atleast one promoter, the at least one participant and the otherparticipant is synchronously changed according to a correspondingsynchronization setting.

In an embodiment, when the at least one of the at least one promoter,the at least one participant and the other participant performs the atleast one operation on the corresponding projected relationalsynchronization workspace, a synchronization command is generated;and/or the synchronization command is transmitted to the correspondingprojected relational synchronization workspace of the at least anotherof the at least one promoter, the at least one participant and the otherparticipant through a client-server architecture or a peer-to-peerarchitecture, so that the projected relational synchronizationworkspaces of the at least one promoter, the at least one participantand the other participant are synchronously changed.

In an embodiment, the at least one participant includes a machine,and/or the at least one other participant includes another machine.

In an embodiment, an operating mode of the projected relationalsynchronization workspace includes a one user to one user mode, a oneuser to multiple user mode or a multiple user to multiple user mode.

In an embodiment, the plurality of unified matters added to theprojectable space instance include at least one matterizer, at least oneunified tool and/or at least one unified information unit, wherein theat least one unified tool and/or the at least one unified informationunit is imported into the corresponding projected relationalsynchronization workspace through the at least one matterizer.

In an embodiment, each of the unified matters is produced after anoriginal matter from at least one information source is unified by theat least one matterizer, wherein each of the unified matters is added tothe projectable space instance.

In an embodiment, at least one original tool corresponding to the atleast one unified tool includes a utility, a widget, an agent, anapplication, a service or any executable element accessible from acorresponding machine or a server, and/or at least one originalinformation corresponding to the at least one unified information unitincludes a file, a web page, a database row, a policy, a rule, a policyof the relational synchronization workspace or any informationaccessible from a corresponding machine or a server.

In an embodiment, the projecting step includes the sub-steps ofacquiring the projectable space instance through a uniform resourceidentifier, and using a projector to parse the projectable spaceinstance to build a working environment, so that the projectedrelational synchronization workspace is executed in the workingenvironment.

In an embodiment, the projector is loaded into an engine that provides acompatible environment to execute the projector.

In an embodiment, the engine includes at least one of a Javascriptengine, a Windows application or a Linux application.

In an embodiment, the projectable space instance is an object, anextensible markup language document, or an instance which isinstantiated with a structured language or a structured protocol.

In accordance with another aspect of the present invention, there isprovided a networking cooperation method. The networking cooperationmethod includes the following steps. Firstly, a plurality of unifiedmatters are combined together into a projectable space instance formodeling a relational synchronization workspace according to anoperational demand. Then, the relational synchronization workspace isprojected to multiple cooperators. The projected relationalsynchronization workspace equips with the plurality of unified mattersaccording to the projectable space instance. At least one cooperator ofthe multiple cooperators accesses the projected relationalsynchronization workspace and cooperatively implement a task with atleast one other cooperator of the multiple cooperators.

In an embodiment, at least two of the multiple cooperators are relatedwith each other according to the operational demand.

In an embodiment, when the at least one cooperator of the multiplecooperators performs at least one operation on the correspondingprojected relational synchronization workspace to result in a change ofthe corresponding projected relational synchronization workspace, theprojected relational synchronization workspace corresponding to the atleast one other cooperator of the multiple cooperators is synchronouslychanged according to a corresponding synchronization setting.

In an embodiment, when the at least one cooperator of the multiplecooperators performs the at least one operation on the correspondingprojected relational synchronization workspace, a synchronizationcommand is generated; and/or the synchronization command is transmittedto the corresponding projected relational synchronization workspace ofthe at least one other cooperator of the multiple cooperators through aclient-server architecture or a peer-to-peer architecture, so that theprojected relational synchronization workspaces of the multiplecooperators are synchronously changed.

In an embodiment, each of the multiple cooperators includes a machine.

In an embodiment, an operating mode of the projected relationalsynchronization workspace includes a one cooperator to one cooperatormode, a one cooperator to multiple cooperator mode or a multiplecooperator to multiple cooperator mode.

In an embodiment, the plurality of unified matters added to theprojectable space instance include at least one matterizer, at least oneunified tool and/or at least one unified information unit, wherein theat least one unified tool and/or the at least one unified informationunit is imported into the corresponding projected relationalsynchronization workspace through the at least one matterizer.

In an embodiment, each of the unified matters is produced after anoriginal matter from at least one information source is unified by theat least one matterizer, wherein each of the unified matters is added tothe projectable space instance.

In an embodiment, the projecting step includes sub-steps of acquiringthe projectable space instance through a uniform resource identifier,and using a projector to parse the projectable space instance to build aworking environment, so that the projected relational synchronizationworkspace is executed in the working environment.

In accordance with a further aspect of the present invention, there isprovided a machine. The machine includes a projector. After the machinereceives a projectable space instance, the projector parses theprojectable space instance to build a projected relationalsynchronization workspace corresponding to the projectable spaceinstance. After the projected relational synchronization workspaceequips a plurality of unified matters that are combined in theprojectable space instance, the machine and at least one cooperatorcooperatively implement a task, or at least one cooperator of multiplecooperators accesses the projected relational synchronization workspaceand cooperate with at least one other cooperator of the multiplecooperators to cooperatively implement the task. The plurality ofunified matters are combined together into the projectable spaceinstance according to an operational demand.

In an embodiment, each of the multiple cooperators comprises an othermachine.

In an embodiment, when the at least one cooperator of the multiplecooperators performs at least one operation on the correspondingprojected relational synchronization workspace to result in a change ofthe corresponding projected relational synchronization workspace, theprojected relational synchronization workspace corresponding to the atleast one other cooperator of the multiple cooperators is synchronouslychanged according to a corresponding synchronization setting.

In an embodiment, the projected relational synchronization workspacecorresponding to the at least one other cooperator of the multiplecooperators is built in at least one other machine.

In an embodiment, at least two of the multiple cooperators are relatedwith each other according to the operational demand.

In an embodiment, the plurality of unified matters added to theprojectable space instance include at least one matterizer, at least oneunified tool and/or at least one unified information unit, wherein theat least one unified tool and/or the at least one unified informationunit is imported into the corresponding projected relationalsynchronization workspace through the at least one matterizer.

In an embodiment, each of the unified matters is produced after anoriginal matter from at least one information source is unified by theat least one matterizer, wherein each of the unified matters is added tothe projectable space instance.

In an embodiment, at least one original tool corresponding to the atleast one unified tool includes a utility, a widget, an agent, anapplication, a service or any executable element accessible from acorresponding machine or a server, and/or at least one originalinformation corresponding to the at least one unified information unitincludes a file, a web page, a database row, a policy, a rule, a policyof the projected relational synchronization workspace, or anyinformation accessible from a corresponding machine or a server.

From the above descriptions, the networking cooperation method of thepresent invention has the following benefits. Since the participants forparticipating in the networking cooperation method can receive the URIthrough the corresponding platforms and/or channels and build thecooperative working environments (i.e., the projected relationalsynchronization workspaces), any identity (including any person or anymachine) can be invited to cooperatively implement the task without theneed of additionally installing an application software or anapplication program in the personal device (e.g., a computer). Secondly,since the working environment for allowing these cooperators tocooperatively implement the task can be unified into a unifiedenvironment by the unifying process, any information, any tool or anyservice can be arbitrarily combined together and compatible with eachother according to the operational demand of any cooperator. Thirdly,any information, any tool or any service in the cooperative workingenvironment (i.e., the projected relational synchronization workspace)can be operated by any cooperator. Moreover, since the cooperativeworking environments (i.e., the projected relational synchronizationworkspaces) for allowing these cooperators to cooperatively implementthe task are projected to and executed in the personal devices (e.g.,computers) of all cooperators, any cooperate can synchronously view thechange of the cooperative working environment in response to anoperation of other cooperator. Fourthly, in comparison with theconventional cooperation method of sharing the screen image, thenetworking cooperation method of the present invention allows thesynchronization command to be transferred between the projectedrelational synchronization workspaces in order to achieve thesynchronizing efficacy. Since the networking cooperation method of thepresent invention only transmits the synchronization command instead oftransmitting the data of the whole screen, the bandwidth usage islargely reduced and the network performance is effectively enhanced.

The above objects and advantages of the present invention will becomemore readily apparent to those ordinarily skilled in the art afterreviewing the following detailed description and accompanying drawings,in which:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating an implementation concept ofa unifying method according to an embodiment;

FIG. 2 is a schematic diagram illustrating an implementation concept ofusing the unified script as an intermediate language for implementingthe personal workspace;

FIG. 3 is a schematic diagram illustrating a preferred configuration ofa personal workspace;

FIG. 4 is a schematic diagram illustrating an initial state of themethod of projecting the workspace according to an embodiment of thepresent invention;

FIGS. 5A and 5B are schematic diagrams illustrating operating conceptsof the method of projecting the workspace as shown in FIG. 4;

FIG. 6 is a schematic diagram illustrating the relationship between aprojectable space instance as shown in FIG. 4 and a projected workspaceas shown in FIG. 5B;

FIG. 7 is a flowchart illustrating a networking cooperation methodaccording to an embodiment of the present invention;

FIG. 8 is a schematic diagram illustrating a usage situation of thenetworking cooperation method according to an embodiment of the presentinvention;

FIG. 9 is a schematic diagram illustrating a process of inviting a firstparticipant and a second participant by a promoter;

FIG. 10 is a schematic diagram illustrating the operating concepts ofthe networking cooperation method applied to the usage situation of FIG.8;

FIG. 11 is a schematic diagram illustrating the relationship between aprojectable space instance and a projected relational synchronizationworkspace according to an embodiment of the present invention;

FIG. 12A is a schematic diagram illustrating the interaction between thefirst participant and the projected relational synchronization workspaceof the first machine of FIG. 10 in an initial state of the networkingcooperation method;

FIG. 12B is a schematic diagram illustrating the interaction between thesecond participant and the projected relational synchronizationworkspace of the second machine of FIG. 10 in an initial state of thenetworking cooperation method;

FIG. 12C is a schematic diagram illustrating the interaction between thepromoter and the projected relational synchronization workspace of thethird machine of FIG. 10 in an initial state of the networkingcooperation method;

FIG. 13A is a schematic diagram illustrating the interaction between thefirst participant and the projected relational synchronization workspaceof the first machine of FIG. 10 after a first presentation material isadded to a blank presentation and edited;

FIG. 13B is a schematic diagram illustrating the interaction between thesecond participant and the projected relational synchronizationworkspace of the second machine of FIG. 10 after the first presentationmaterial is added to the blank presentation and edited by the firstparticipant;

FIG. 13C is a schematic diagram illustrating the interaction between thepromoter and the projected relational synchronization workspace of thethird machine of FIG. 10 after the first presentation material is addedto the blank presentation and edited by the first participant;

FIG. 14A is a schematic diagram illustrating the interaction between thefirst participant and the projected relational synchronization workspaceof the first machine of FIG. 10 after a second presentation material isadded to the presentation with the first unified presentation materialand edited by the second participant;

FIG. 14B is a schematic diagram illustrating the interaction between thesecond participant and the projected relational synchronizationworkspace of the second machine of FIG. 10 after the second presentationmaterial is added to the presentation with the first unifiedpresentation material and edited by the second participant;

FIG. 14C is a schematic diagram illustrating the interaction between thepromoter and the projected relational synchronization workspace of thethird machine of FIG. 10 after the second presentation material is addedto the presentation with the first unified presentation material andedited by the second participant;

FIG. 15 is a schematic diagram illustrating the use of the client-serverarchitecture to synchronize the projected relational synchronizationworkspaces in different machines;

FIG. 16 is a schematic diagram illustrating the use of the peer-to-peerarchitecture to synchronize the projected relational synchronizationworkspaces in different machines; and

FIG. 17 is a schematic diagram illustrating a usage situation of anetworking cooperation method according to another embodiment of thepresent invention.

DETAILED DESCRIPTION

The present invention is more fully appreciated by reference to thefollowing description, including the following glossary of terms and theconcluding examples. For the sake of brevity, the disclosures of thepublications, including patents, cited in this specification are hereinincorporated by reference.

The examples below are non-limiting and are merely representative ofvarious aspects and features of the present invention. The term“information source” used herein is defined as a sequence of symbolsthat can be interpreted as a message in the most limited technicalmeaning. And the message is used for organizing and labelinginformation. For example, the information source includes website (suchas internet service), intranet, social network, software, electronicbook, database and other media of information (such as storage media ofnon-transitory computer or storage media of mobile device). The term“original information” used herein is a file, a web page, a databaserow, a policy, a rule or any data accessible in corresponding machinesand servers, but is not limited thereto. The term “original tool” usedherein is a utility, a widget, an intelligent agent, an application, aservice or any executable component accessible in corresponding machinesand servers, but is not limited thereto. It is noted that theinformation sources, the original information and the original tool arenot restricted to the above examples.

Moreover, “original information” and “original tool” are implementationexamples of “original matters” used herein. In accordance with thepresent invention, a plurality of “original matters” from identical ordifferent “information sources” are modeled to a plurality of “unifiedmatters” by a unifying method. Consequently, the “unified matters” inthe same execution environment are compatible with each other andcooperate to perform a specified task. The “unified tool” and the“unified information unit” are implementation examples of the “unifiedmatters”. Moreover, the term “Matterizer” used herein is a means, adevice or a program code to perform the unifying process.

In an embodiment, the above unifying method comprises steps of: modelingat least one original information obtained from at least one informationsource of multiple information sources into a unified information unitwith one unified data model via re-organizing the original information,and/or modeling at least one original tool obtained from at least oneinformation source of multiple information sources into a unified toolwith another unified data model via re-organizing the original tool. Theone unified data model and another unified data model could be identicalor different, and the unifying method described above could be completedthrough a matterizer.

Please refer to FIG. 1. FIG. 1 is a schematic diagram illustrating animplementation concept of a unifying method according to an embodiment.As shown in FIG. 1, the matterizer 992 re-organizes an attribute and alink of an original matter 991 with a unified data model 993, and thusmodels the original matter 991 into a unified matter 994. Consequently,the basic attribute of the unified matter 994 include a type of theoriginal matter 994 and a link indicating where the original matter 994is located.

In this embodiment, the original matter 991 at least includes anoriginal information (not shown) or an original tool (not shown), but isnot limited thereto. In the above unifying method, if the attributeaccessible from the original information corresponds to the attribute tobe unified in the unified information unit, the unified information unitis directly produced through the matterizer 992. If the attributeaccessible from the original information does not correspond to theattribute to be unified in the unified information unit, the originalinformation is firstly re-defined by logically re-organizing theattributes and the link of the original information, and then theoriginal information is converted into a new original information withthe attributes which correspond to attributes to be unified in theunified information unit. Consequently, the unified information unit isindirectly produced.

Moreover, if the original tool is compatible with the workingenvironment of the workspace, the unified tool is directly produced bythe matterizer 992. On the other hand, if the original tool isincompatible with the working environment of the workspace, the unifiedtool is indirectly produced via an adapter and/or a software developmentkit (SDK) of the original tool to drive the original tool. The adapterprovides an interface implementation compatible with the workingenvironment.

Herein, “the descriptions of the unifying method”, “the methods ofobtaining the unified matters” and “the descriptions of the matterizer”may be referred to the U.S. patent application Ser. No. 14/324,069,entitled “A method of unifying information and tool from a plurality ofinformation sources”, and also referred to the China Patent ApplicationNo. 201410768564.X, which claims the benefit of priority to the U.S.patent application Ser. No. 14/324,069 and is entitled “A method ofunifying information and tool from a plurality of information sourcesand computer product and device using the method”. The detaileddescriptions thereof are omitted.

The above unifying method is presented herein for purpose ofillustration and description only. The method of unifying a plurality oforiginal matters from different information sources is not restricted.However, those skilled in the art will readily observe that numerousmodifications and alterations may be made while retaining the teachingsof the invention.

Hereinafter, two other unifying methods will be illustrated. The firstunifying method is applied to a method of unifying the information ofGarmin satellite navigation. Through a point-of-interest (POI) functionof the Garmin satellite navigation, the method of unifying theinformation is employed to unify the imported original point information(i.e., an original information) into the corresponding unified pointinformation (i.e., a unified information unit). The second unifyingmethod is applied to a method of unifying the tool of an Android system.The Android system is a Linux-based open source mobile operating system.However, most application programs (i.e., original tools) are written inthe Java programming language. Consequently, the application program(i.e., the original tool) written in the Java programming language canbe modelled into a unified application program (i.e., the unified tool)compatible with the Android system so as to be executed in the Androidsystem.

The term “workspace” used herein is a working environment for providinginteractions between the at least one matterizer, the at least one tooland/or the at least one information so as to implement a specified task.Moreover, the at least one tool and/or at least one information can beimported into the workspace through the at least one matterizer.However, the way of importing the information and/or tool into theworkspace is not restricted. Hereinafter, information importers such asthe information importers 9881, 9882 and 9883 of FIG. 2, the Dropboximporter 9761′ of FIG. 6 and the information importers 52 of FIGS. 11,12A˜12C, FIGS. 13A˜13C and FIGS. 14A˜14C are some examples of thematterizer. The term “unified script” used herein is an intermediatelanguage to implement the workspace. Moreover, via the “unified script”,the at least one matterizer, the at least one tool and/or the at leastone information can be provided to the workspace (e.g., built in orplugged in the workspace).

In an embodiment, the above at least one information is a unifiedinformation unit which is produced after at least one originalinformation obtained from at least one information source is unified,and the above at least one tool is a unified tool which is producedafter at least one original tool obtained from at least one informationsource is unified. Moreover, according to different tasks, the requiredunified information unit and/or the required unified tool from thecorresponding information source can be added to the personal workspace(e.g., built in or plugged in the personal workspace). In other words,the “workspace” is a user-orientated “personal workspace”.

Please refer to FIG. 2 and FIG. 3. FIG. 2 is a schematic diagramillustrating an implementation concept of using the unified script as anintermediate language for implementing the workspace. FIG. 3 is aschematic diagram illustrating a preferred configuration of a personalworkspace. As shown in FIG. 2 and FIG. 3, a unified information unit985′ corresponding to an original information 985 in Dropbox 982, afirst unified tool 986′ corresponding to a compatible original tool 986in a cloud storage 983 and a second unified tool 987′ corresponding toan incompatible original tool 987 in a server 984 are combined togetherinto a personal workspace 981 according to the required tasks. Inparticular, a unified script 980 which is regarded as an intermediatelanguage for implementing the personal workspace 981 is firstlycompiled, and then an information importer 9881 of the Dropbox 982, aninformation importer 9882 of the cloud storage 983 and an informationimporter 9883 of the server 984 are configured through the unifiedscript 980. Moreover, after the original information 985 in the Dropbox982 is unified into the unified information unit 985′ by the informationimporter 9881, the unified information unit 985′ is imported into thepersonal workspace 981.

As shown in FIG. 2 and FIG. 3, the original tool stored in the cloudstorage 983 is the compatible original tool 986, which is compatiblewith the component architecture of the unified tool in the personalworkspace 981. Moreover, the first unified tool 986′ corresponding tothe compatible original tool 986 is directly provided to the personalworkspace 981 through the information importer 9882 of the unifiedscript 980.

As shown in FIG. 2 and FIG. 3, the original tool stored in the server984 is the incompatible original tool 987, which is incompatible withthe component architecture of the unified tool in the personal workspace981. Moreover, the second unified tool 987′ corresponding to theincompatible original tool 987 is provided to the personal workspace 981through the compatible adapter 989 and the information importer 9883 ofthe unified script 980.

As shown in FIG. 3, the user can configure and arrange (e.g., group orplace) the unified information unit 985′, the first unified tool 986′and the second unified tool 987′ in a specific area of the personalworkspace 981 according to the practical requirements. Moreover,according to the operational relationship between the unified tool andthe unified information unit (e.g., the clicking or dragging actionsbetween the two), the user can perform specified tasks by using theunified tool to access or control the corresponding unified informationunit.

Herein, “the descriptions of using the unified script as theintermediate language for implementing the personal workspace” and “thedescriptions of allowing the required unified information unit and/orthe required unified tool from the corresponding information sources tobe arbitrarily combined together into the personal workspace accordingto the practical requirements” may be referred to the U.S. patentapplication Ser. No. 14/325,466, entitled “Method for performing task onunified information units in a personal workspace”, and also referred tothe China Patent Application No. 201410768564.X, which claims thebenefit of priority to the U.S. patent application Ser. Nos. 14/324,069and 14/325,466 and is entitled “A method of combining unified matters ina personal workspace and computer product and device using the method”.The detailed descriptions thereof are omitted.

The above personal workspace is presented herein for purpose ofillustration and description only. It is noted that the workspace usedin the present invention is not restricted. For example, the unifiedscript as the intermediate language for implementing the workspace canbe previously edited. Consequently, the workspace has the defaultmatterizer, the default information and/or the default tool. Thisworkspace is not limited to be operated by a single user. According tothe practical requirements, this workspace can be operated by multipleusers at the same time or at different times.

Moreover, the “workspace” used herein is obtained by “a method ofprojecting a workspace” to any electronic device with computationalcapability. An example of the electronic device includes but is notlimited to a mobile phone, a tablet computer, a notebook computer or adesktop computer. Consequently, the “projected workspace” can beoperated by any user through any electronic device with computationalcapability.

In an embodiment, the method of projecting the workspace comprises thefollowing steps. Firstly, a projectable space instance instantiated bythe unified script is obtained through a uniform resource identifier(URI). As mentioned above, the unified script is defined to configure atleast one of the matterizer, the information and the tool to model theworkspace. Moreover, the projectable space instance is used to build theprojected workspace corresponding to the workspace, and thus provide aninterface for operating at least one of the matterizer, the informationand the tool to implement a task. Then, a projector parses theprojectable space instance and build a working environment to configureat least one of the matterizer, the information and the tool so as toexecute the projected workspace for providing interactions between atleast one user and the projected workspace.

The projector is acquired from a remote data station, the projectablespace instance or a preloaded application program, and loaded into anengine for providing a compatible environment to execute the projector.An example of the engine includes but is not limited to a Javascriptengine, a Windows application or a Linux application. Preferably but notexclusively, the united script can be declared by a document typedefinition (DTD), an extensible markup language (XML) Schema, astructured language or a structured protocol. Preferably but notexclusively, the projectable space instance is an object, an extensiblemarkup language (XML) document, or an instance instantiated with astructured language or a structured protocol.

Please refer to FIG. 4, FIG. 5A, FIG. 5B and FIG. 6. FIG. 4 is aschematic diagram illustrating an initial state of the method ofprojecting the workspace according to an embodiment of the presentinvention. FIGS. 5A and 5B are schematic diagrams illustrating operatingconcepts of the method of projecting the workspace as shown in FIG. 4.FIG. 6 is a schematic diagram illustrating the relationship between aprojectable space instance as shown in FIG. 4 and a projected workspaceas shown in FIG. 5B.

In the initial state of FIG. 4, a first electronic device 971 and asecond electronic device 972 are in communication with each other (e.g.,through network connection). Moreover, the first electronic device 971stores a projectable space instance 973, and the second electronicdevice 972 has a built-in projector 974.

In this embodiment, the united script 9731 is declared by a documenttype definition (DTD) and defined to configure at least one informationimporter (i.e., an example of the matterizer), at least one unifiedinformation unit and/or at least one unified tool to model a workspace,and the projectable space instance 973 is an instance instantiated withthe extensible markup language (XML). As shown in FIG. 6, theprojectable space instance 973 is used for building a projectedworkspace 976 corresponding to the workspace. Moreover, the informationimporter, the unified information and/or the unified tool is allowed tobe added to or removed from the projectable space instance 973.

The projector 974 of the second electronic device 972 will build aworking environment 975 in the second electronic device 972 forexecuting the projected workspace 976. In addition, the projector 974provides a microkernel 977 (see FIG. 6) to the working environment 975for equipping at least one information importer, at least one unifiedinformation and/or at least one unified tool that will be added to theprojected workspace 976. When the second electronic device 972 acquiresthe projectable space instance 973 from the first electronic device 971through a URI, the projector 974 of the second electronic device 972starts to parse the projectable space instance 973 (see FIG. 5A). Afterthe projectable space instance 973 is parsed by the projector 974, theprojected workspace 976 is built in the working environment 975according to parsed contents of the projectable space instance 973 (seeFIG. 5B). Accordingly, a user of the second electronic device 972 caninteract with the projected workspace 976 through the second electronicdevice 972 so as to perform related tasks.

The relationships between the unified script 9731, the projectable spaceinstance 973 and the projected workspace 976 will be illustrated in moredetailed through a usage situation as shown in FIG. 6. The usagesituation as shown in FIG. 6 is related to a process of building aprojected workspace that is capable of accessing jpg format image filesand gif format image files from a specified internet space and allowingthe image files to be viewed by a user. In this usage situation, theunified script 9731 is declared by the Document Type Definition (DTD),and the projectable space instance 973 is instantiated with XML.

Moreover, an information importer and a unified tool are added into theprojectable space instance 973, and at least one unified informationunit corresponding to the original information is imported into theprojected workspace 976 through the information importer. In this usagesituation, the information importer is a Dropbox importer. Theinformation of the Dropbox importer is disclosed in the dashed lineframe 9761 of FIG. 6. The original information includes a jpg formatimage file 9791, a jpg format image file 9792 and a gif format imagefile 9793 in Dropbox 979 (i.e., an information source). The unifiedinformation units includes a unified jpg format image file 9791′, aunified jpg format image file 9792′ and a unified gif format image file9793′, which will be described later. The unified tool is an imageviewer for accessing image files which are imported into the projectedworkspace 976. The information of the image viewer is disclosed in thedashed line frame 9762 of FIG. 6.

As mentioned above, the projected workspace 976 is built after theprojectable space instance 973 is parsed by the projector 974 of thesecond electronic device 972. In this embodiment, the Dropbox importer9761′ corresponding to the dashed line frame 9761 and the image viewer9762′ corresponding to the dashed line frame 9762 are configured in theprojected workspace 976. Moreover, the jpg format image file 9791, thejpg format image file 9792 and the gif format image file 9793 in Dropbox979 are unified and imported into the projected workspace 976 by theDropbox importer 9761′. Consequently, the unified jpg format image file9791′ corresponding to the jpg format image file 9791, the unified jpgformat image file 9792′ corresponding to the jpg format image file 9792and the unified gif format image file 9793′ corresponding to the gifformat image file 9793 are displayed on the projected workspace 976.When the user of the second electronic device 972 manipulates any of theunified image files 9791′, 9792′ and 9793′ by any specified operatingmeans (such as an action of clicking any of the unified images files9791′, 9792′ and 9793′ or an action of dragging and dropping any of theimage files 9791′, 9792′ and 9793′ to the image viewer 9762′), the imageviewer 9762′ will access the contents of the corresponding unified imagefiles 9791′, 9792′ or 9793′ to allow the unified image files 9791′,9792′ or 9793′ to be viewed by the user. Moreover, the Dropbox importer9761′ and the image viewer 9762′ mentioned above are equipped by themicrokernel 977.

It is noted that the URI of the projectable space instance 973 may be aHTTP (hypertext transfer protocol) URI or a FTP (file transfer protocol)URI. In case that the first electronic device 971 and the secondelectronic device 972 are integrated into one device, the URI of theprojectable space instance 973 can also be a local file URI. However,the types of the URI of the projectable space instance 973 are notrestricted.

Herein, “the descriptions of the method of projecting the workspace” maybe referred to the U.S. patent application Ser. No. 14/577,772, entitled“Method of projecting a workspace and system using the same”, and alsoreferred to the China Patent Application No. 201410814138.5, whichclaims the benefit of priority to the U.S. patent application Ser. Nos.14/324,069, 14/325,466 and 14/577,772 and is entitled “Method ofprojecting a workspace and system using the same”. The detaileddescriptions thereof are omitted.

The above method of projecting the workspace to any electronic devicewith computational capability is presented herein for purpose ofillustration and description only. The method of projecting theworkspace to any electronic device with computational capability is notrestricted. However, those skilled in the art will readily observe thatnumerous modifications and alterations may be made while retaining theteachings of the invention.

Moreover, any workspace can be projected to any electronic device withcomputational capability. That is, any workspace can be delivered to anyelectronic device with computational capability. Consequently, theworkspace is also a working platform for allowing multiple cooperatorsto cooperatively implement the task. That is, the workspace is a“relational synchronization workspace”. The present invention provides anetworking cooperation method on network and a machine using thenetworking cooperation method, which will be illustrated in more detailsas follows.

FIG. 7 is a flowchart illustrating a networking cooperation methodaccording to an embodiment of the present invention. The networkingcooperation method includes the following steps:

Step P1: Combine a plurality of unified matters together into aprojectable space instance for modeling a relational synchronizationworkspace according to an operational demand from at least one promoter;and

Step P2: Project the relational synchronization workspace to at leastone participant, wherein the projected relational synchronizationworkspace equips the plurality of unified matters according to theprojectable space instance, wherein the at least one participantaccesses the projected relational synchronization workspace tocooperatively implement a task with the at least one promoter and/or atleast one other participant.

Please refer to FIGS. 8˜11. FIG. 8 is a schematic diagram illustrating ausage situation of the networking cooperation method according to anembodiment of the present invention. FIG. 9 is a schematic diagramillustrating a process of inviting a first participant and a secondparticipant by a promoter. FIG. 10 is a schematic diagram illustratingthe operating concepts of the networking cooperation method applied tothe usage situation of FIG. 8. FIG. 11 is a schematic diagramillustrating the relationship between a projectable space instance and aprojected relational synchronization workspace according to anembodiment of the present invention.

This embodiment is related to the following usage situation. That is, apromotor 23 intends to invite a first participant 21 and a secondparticipant 22 to cooperatively make a topical presentation.Hereinafter, the promotor 23, the first participant 21 and the secondparticipant 22 are collaboratively referred as cooperators 2. Accordingto an operational demand of “making a topical presentation”, thesecooperators 2 are related with each other. Before the networkingcooperation method starts, the promotor 23 installs a projectable spaceinstance 3 in a fourth machine 14. The projectable space instance 3 isused for modeling a relational synchronization workspace. According tothe operational demand of making the topical presentation and a requiredcommunication means for cooperation, the required unified matters 5 arecombined together into the projectable space instance 3 by the promotor23. In this embodiment, the unified tools 51 added to the projectablespace instance 3 include a presentation reader 511, a presentationeditor 512, a video caller 513 and a recorder 514.

In this embodiment, as shown in FIG. 11, the projectable space instance3 is an instance instantiated with the extensible markup language (XML).FIG. 11 also shows the compiled contents of the projectable spaceinstance 3 and the relationships between the compiled contents of theprojectable space instance 3 and the unified matters 5 of a projectedrelational synchronization workspace 6. In FIG. 11, the both ends ofeach dotted line denote the compiled contents of the projectable spaceinstance 3 and the corresponding unified matters 5 in the relationship.

Moreover, in the usage situation of FIG. 8, a first machine 11, a secondmachine 12 and a third machine 13 are operated by the first participant21, the second participant 22 and the promotor 23, respectively.Moreover, each of the first machine 11, the second machine 12 and thethird machine 13 has a projector 4. Preferably but not exclusively, theprojector 4 is at least acquired from a remote station (not shown), theprojectable space instance 3 in the fourth machine 14 or a preloadedapplication program (not shown) in the first machine 11, the secondmachine 12 and the third machine 13.

In this embodiment, the first machine 11, the second machine 12 and thethird machine 13 are connected with the fourth machine 14 directly orindirectly (e.g., through network connection as indicated by dottedlines as shown in FIG. 10). Consequently, the projectable space instance3 can be transmitted from the fourth machine 14 to the first machine 11,the second machine 12 and the third machine 13. In addition, anyoriginal matter (e.g., the first presentation material or tool in thefirst machine 11, the second presentation material or tool in the secondmachine 12, the third presentation material or tool in the third machine13 and the data or executable element accessible from a correspondingmachine or a server) can be provided to the fourth machine 14 afterbeing unified.

Please refer to the step P2 of FIG. 7 and FIG. 9. The projectable spaceinstance 3 has the corresponding uniform resource identifier (URI). Whenthe promotor 23 intends to invite multiple participants to cooperativelymake a topical presentation 5, the promoter 23 issues the URI of theprojectable space instance 3 to the first participant 21 and the secondparticipant 22 through a platform and/or a channel. Consequently, thefirst participant 21 and the second participant 22 can load theprojectable space instance 3 into the first machine 11 and the secondmachine 12 through the URI. Similarly, through the URI, the promoter 23can load the projectable space instance 3 into the third machine 13which is operated by the promoter 23. For example, the platform fortransmitting the URI is an operating system or a browser, and thechannel for transmitting the URI is an e-mail, an intranet, a socialnetwork, a blog, a web site or a chat communication channel. The type ofthe platform and the type of the channel are presented herein forpurpose of illustration and description only.

Please refer to the step P2 of FIG. 7 and FIG. 10. The projectors 4 inthe first machine 11, the second machine 12 and the third machine 13build the working environments 41 in the first machine 11, the secondmachine 12 and the third machine 13. Consequently, the projectedrelational synchronization workspaces 6A, 6B and 6C are executed in theworking environments 41. In addition, the projectors 4 providemicrokernels 61 corresponding to the projected relationalsynchronization workspaces 6A, 6B and 6C (see FIGS. 12A˜12C, FIGS.13A˜13C and FIGS. 14A˜14C) in order for equipping unified matters 5 thatare compiled in the projectable space instance 3. For example, theunified matters 5 include unified tools 51 and information importers 52.After the first machine 11, the second machine 12 and the third machine13 acquire the projectable space instance 3 from the fourth machine 14through the URI, the projectors 4 start to parse the projectable spaceinstance 3. After the projectable space instance 3 is parsed by theprojectors 4, the projected relational synchronization workspaces 6A, 6Band 6C are built in the working environment according to parsed contentsof the projectable space instance 3. Consequently, the first participant21 of the first machine 11, the second participant 22 of the secondmachine 12 and the promotor of the third machine 13 can interact withthe projected relational synchronization workspaces 6A, 6B and 6Cthrough the first machine 11, the second machine 12 and the thirdmachine 13, respectively. That is, these cooperators 2 can operate thecorresponding projected relational synchronization workspaces 6A, 6B and6C so as to cooperatively implement a specified task.

Hereinafter, a process of cooperatively implementing a task by thesecooperators 2 according to the networking cooperation method of thepresent invention will be illustrated with reference to FIGS. 12A˜12C,FIGS. 13A˜13C and FIGS. 14A˜14C.

FIG. 12A is a schematic diagram illustrating the interaction between thefirst participant and the projected relational synchronization workspaceof the first machine of FIG. 10 in an initial state of the networkingcooperation method. FIG. 12B is a schematic diagram illustrating theinteraction between the second participant and the projected relationalsynchronization workspace of the second machine of FIG. 10 in an initialstate of the networking cooperation method. FIG. 12C is a schematicdiagram illustrating the interaction between the promoter and theprojected relational synchronization workspace of the third machine ofFIG. 10 in an initial state of the networking cooperation method. FIG.13A is a schematic diagram illustrating the interaction between thefirst participant and the projected relational synchronization workspaceof the first machine of FIG. 10 after a first presentation material isadded to a blank presentation and edited. FIG. 13B is a schematicdiagram illustrating the interaction between the second participant andthe projected relational synchronization workspace of the second machineof FIG. 10 after the first presentation material is added to the blankpresentation and edited by the first participant. FIG. 13C is aschematic diagram illustrating the interaction between the promoter andthe projected relational synchronization workspace of the third machineof FIG. 10 after the first presentation material is added to the blankpresentation and edited by the first participant. FIG. 14A is aschematic diagram illustrating the interaction between the firstparticipant and the projected relational synchronization workspace ofthe first machine of FIG. 10 after a second presentation material isadded to the presentation with the first unified presentation materialand edited by the second participant. FIG. 14B is a schematic diagramillustrating the interaction between the second participant and theprojected relational synchronization workspace of the second machine ofFIG. 10 after the second presentation material is added to thepresentation with the first unified presentation material and edited bythe second participant. FIG. 14C is a schematic diagram illustrating theinteraction between the promoter and the projected relationalsynchronization workspace of the third machine of FIG. 10 after thesecond presentation material is added to the presentation with the firstunified presentation material and edited by the second participant.

Please refer to FIGS. 12A˜12C. In the initial state of the usagesituation, the projected relational synchronization workspaces 6A, 6Band 6C are built in the first machine 11, the second machine 12 and thethird machine 13, respectively. A blank presentation 53 is firstlyunified, and then imported into the projected relational synchronizationworkspaces 6A, 6B and 6C through the information importers 52. Moreover,the blank presentation 53 is shown to be viewed by the first participant21, the second participant 22 and the promotor 23 through thepresentation readers 511. FIG. 12A shows the projected relationalsynchronization workspace 6A built in the first machine 11 in theinitial state. FIG. 12A also shows the presentation reader 511, thepresentation editor 512 and the video caller 513 in addition to theblank presentation 53. The photo images of the second participant 22 andthe promoter 23 are shown on the video caller 513 for facilitating thefirst participant 21 to communicate and discuss with the secondparticipant 22 and the promoter 23. By operating the presentation editor512, the first participant 21 can edit the presentation 53 shown on theprojected relational synchronization workspace 6A. By operating therecorder 514, the first participant 21 can record the cooperatingprocess of these cooperators 2. The recorded contents include imageinformation, sound information, and so on. Moreover, the recordedcontents can be stored in a specified storage area. Moreover, as shownin FIG. 12A, the first participant 21 is ready to add a firstpresentation material 54 to the blank presentation 53 and edit the blankpresentation 53 through the presentation editor 512 while thesecooperators 2 communicate and discuss with each other.

Similarly, FIG. 12B shows the projected relational synchronizationworkspace 6B built in the second machine 12 in the initial state. FIG.12B also shows the presentation reader 511, the presentation editor 512and the video caller 513 in addition to the blank presentation 53. Thephoto images of the first participant 21 and the promoter 23 are shownon the video caller 513 for facilitating the second participant 22 tocommunicate and discuss with the first participant 21 and the promoter23. By operating the presentation editor 512, the second participant 22can edit the presentation 53 shown on the projected relationalsynchronization workspace 6B. By operating the recorder 514, the secondparticipant 22 can record the cooperating process of these cooperators2. The recorded contents include image information, sound information,and so on. Moreover, the recorded contents can be stored in a specifiedstorage area.

Similarly, FIG. 12C shows the projected relational synchronizationworkspace 6C built in the third machine 13 in the initial state. FIG.12C also shows the presentation reader 511, the presentation editor 512and the video caller 513 in addition to the blank presentation 53. Thephoto images of the first participant 21 and the second participant 22are shown on the video caller 513 for facilitating the promoter 23 tocommunicate and discuss with the first participant 21 and the secondparticipant 22. By operating the presentation editor 512, the promoter23 can edit the presentation 53 shown on the projected relationalsynchronization workspace 6C. By operating the recorder 514, thepromoter 23 can record the cooperating process of these cooperators 2.The recorded contents include image information, sound information, andso on. Moreover, the recorded contents can be stored in a specifiedstorage area.

After the first participant 21 adds the first presentation material 54to the blank presentation 53 and edit the blank presentation 53, thecontents of the projected relational synchronization workspaces 6A, 6Band 6C are shown in FIGS. 13A˜13C. When the first participant 21 addsthe first presentation material 54 to the blank presentation 53 (e.g.,by dragging the first presentation material 54 to the blank presentation53), the first presentation material 54 is unified into a first unifiedpresentation material 54′ through the information importer 52. From thedrawings, it is found that the presentations 53 in the projectedrelational synchronization workspaces 6B and 6C are synchronouslychanged when the presentation 53 in the projected relationalsynchronization workspace 6A is changed in response to the operation ofthe first participant 21. In other words, the presentation 53 in each ofthe projected relational synchronization workspaces 6A, 6B and 6Ccontains the first unified presentation material 54′ and the editedresult of the first participant 21.

As shown in FIG. 13B, while these cooperators 2 communicate and discusswith each other, the second participant 22 is ready to add a secondpresentation material 55 to the presentation 53, which contains thefirst unified presentation material 54′ and has been edited by the firstparticipant 21. Moreover, through the presentation editor 512 of theprojected relational synchronization workspace 6B, the presentation 53with the first unified presentation material 54′ can be edited by thesecond participant 22.

After the second participant 22 adds the second presentation material 55to the presentation 53 and edit the blank presentation 53, the contentsof the projected relational synchronization workspaces 6A, 6B and 6C areshown in FIGS. 14A˜14C. When the second participant 22 adds the secondpresentation material 55 to the blank presentation 53 (e.g., by draggingthe second presentation material 55 to the blank presentation 53), thesecond presentation material 55 is unified into a second unifiedpresentation material 55′ through the information importer 52. From thedrawings, it is found that the presentations 53 in the projectedrelational synchronization workspaces 6A and 6C are synchronouslychanged when the presentation 53 in the projected relationalsynchronization workspace 6B is changed in response to the operation ofthe second participant 22. In other words, the presentation 53 in eachof the projected relational synchronization workspaces 6A, 6B and 6Ccontains the first unified presentation material 54′, the second unifiedpresentation material 55′ and the edited results of the firstparticipant 21 and the second participant 22.

As mentioned above, when any cooperator operates the correspondingprojected relational synchronization workspace and results in a changeof the corresponding projected relational synchronization workspace, theprojected relational synchronization workspaces corresponding to theother cooperators are synchronously changed. For achieving the abovepurpose, the present invention further provides the followingsynchronization process. When the projected relational synchronizationworkspace in any machine is accessed, a corresponding synchronizationcommand is generated. In addition, the synchronization command istransmitted to the projected relational synchronization workspaces ofthe other machines. According to the synchronization command, theseprojected relational synchronization workspaces are synchronouslychanged. The synchronization process may be implemented withclient-server architecture, peer-to-peer architecture or the like.

FIG. 15 is a schematic diagram illustrating the use of the client-serverarchitecture to synchronize the projected relational synchronizationworkspaces in different machines. In the client-server architecture, allof the first machine 11, the second machine 12 and the third machine 13are connected with a server 8. The synchronization command from any ofthe first machine 11, the second machine 12 and the third machine 13 canbe transmitted to the other two of the first machine 11, the secondmachine 12 and the third machine 13 through the server 8.

As shown in FIG. 15, the projected relational synchronization workspace6A in the first machine 11 issues a synchronization command D1 inresponse to an operation of the first participant 21. After thesynchronization command D1 is received by the server 8, thesynchronization command D1 is transmitted to the projected relationalsynchronization workspace 6B in the second machine 12 and the projectedrelational synchronization workspace 6C in the third machine 13.Consequently, the contents of the projected relational synchronizationworkspaces 6A, 6B and 6C are synchronized in response to the operationof the first participant 21. Similarly, when the second participant 22of the second machine 12 accesses the corresponding projected relationalsynchronization workspace 6B or when the promoter 23 of the thirdmachine 13 accesses the corresponding projected relationalsynchronization workspace 6C, the synchronization process is alsoimplemented.

FIG. 16 is a schematic diagram illustrating the use of the peer-to-peerarchitecture to synchronize the projected relational synchronizationworkspaces in different machines. In the peer-to-peer architecture, allof the first machine 11, the second machine 12 and the third machine 13can realize the network locations of other machines through the fourthmachine 14. Consequently, the first machine 11, the second machine 12and the third machine 13 are in communication with each other throughnetwork connection. Meanwhile, the synchronization command from any ofthe first machine 11, the second machine 12 and the third machine 13 canbe transmitted to the other two of the first machine 11, the secondmachine 12 and the third machine 13 directly.

As shown in FIG. 16, the projected relational synchronization workspace6B in the second machine 12 issues a synchronization command D2 inresponse to an operation of the second participant 22. Consequently, thesynchronization command D2 is directly transmitted to the projectedrelational synchronization workspace 6A in the first machine 11 and theprojected relational synchronization workspace 6C in the third machine13. Consequently, the contents of the projected relationalsynchronization workspaces 6A, 6B and 6C are synchronized in response tothe operation of the second participant 22. Similarly, when the firstparticipant 21 of the first machine 11 accesses the correspondingprojected relational synchronization workspace 6A or when the promoter23 of the third machine 13 accesses the corresponding projectedrelational synchronization workspace 6C, the synchronization process isalso implemented.

The synchronization process and the architecture for implementing thesynchronization process are presented herein for purpose of illustrationand description only. However, those skilled in the art will readilyobserve that numerous modifications and alterations may be made whileretaining the teachings of the invention.

Preferably but not exclusively, a synchronization setting about thechange of the corresponding projected relational synchronizationworkspace in response to any operation may be determined by anycooperator 2 according to the practical requirements. For example,during the cooperating process, the first participant 21 may remarkrelevant attentive items (not shown) or make notes (not shown) on theprojected relational synchronization workspace 6A. If the firstparticipant 21 sets that the attentive items or notes are notsynchronized, the attentive items or notes will not be displayed on theprojected relational synchronization workspace 6B of the secondparticipant 22 and the projected relational synchronization workspace 6Cof the promoter 23. For example, during the cooperating process, thepromoter 23 may configure a toolbar (not shown) containing a pluralityof unified tools (not shown) in the projected relational synchronizationworkspace 6C so as to facilitate operation. If the promoter 23 intendsto share the toolbar with the second participant 22 only, the promoter23 may set the synchronization of the toolbar. Consequently, the toolbaris only synchronously shown on the projected relational synchronizationworkspace 6B of the second participant 22.

Moreover, while these cooperators 2 communicate and discuss with eachother, any of these cooperators 2 may invite other participants tocooperatively implement the task. For example, if the second participant22 meets with obstruction while making a topical presentation, thesecond participant 22 may invite another participant (e.g., a thirdparticipant, not shown) to ask for help. Under this circumstance, theURI of the projectable space instance 3 can be transmitted to the thirdparticipant through the platform and/or channel which is frequently usedby the third participant. Consequently, the third participant can loadthe projectable space instance 3 into the own machine through the URI.After the projected relational synchronization workspace is built, thethird participant can cooperatively implement the task with the promoter23, the first participant 21 and the second participant 22. Moreover,while these cooperators 2 communicate and discuss with each other, anyof these cooperators 2 can provide another unified matter 5 (e.g., aphoto edit tool, not shown) to the projected relational synchronizationworkspaces 6A, 6B and 6C at any time according to the practicalrequirements.

The operating mode of the networking cooperation method includes a onecooperator to one cooperator mode, a one cooperator to multiplecooperator mode (e.g., a broadcasting method), or a multiple cooperatorto multiple cooperator mode. Alternatively, in some other embodiments,these cooperators are machines. Furthermore, another usage situation ofthe networking cooperation method will be illustrated as follows.

FIG. 17 is a schematic diagram illustrating a usage situation of anetworking cooperation method according to another embodiment of thepresent invention. The embodiment is related to the following usagesituation. That is, a cable TV setting staff 74 intends to set a firstinternet TV box 71, a second internet TV box 72 and a third internet TVbox 73 at different families in order to cooperatively implement anetwork playing task. The first internet TV box 71, the second internetTV box 72 and the third internet TV box 73 have corresponding projectors4′. After the projectors 4′ receive the projectable space instance 3′through the URI, the projectors 4′ automatically parse the projectablespace instance 3′. Consequently, a working environment 41′ is built toexecute the projected relational synchronization workspaces 6A′, 6B′ and6C′. In this embodiment, the cable TV setting staff 74 is a promoter,and the first internet TV box 71, the second internet TV box 72 and thethird internet TV box 73 are participants. Moreover, the cable TVsetting staff 74 is related with the first internet TV box 71, thesecond internet TV box 72 and the third internet TV box 73 according toan operational demand of cooperatively implementing a network playingtask. Before the networking cooperation method starts, the cable TVsetting staff 74 installs the projectable space instance 3′ in a fourthmachine 14. The projectable space instance 3′ is used for modeling arelational synchronization workspace. Moreover, according to theoperational demand of cooperatively implementing a network playing task,a video play tool (not shown) and a video playlist (not shown) arecombined together into the projectable space instance 3′ by the cable TVsetting staff 74. Meanwhile, the projected relational synchronizationworkspaces 6A′, 6B′ and 6C′ are configured in the working environments41′ of the first internet TV box 71, the second internet TV box 72 andthe third internet TV box 73. After the networking cooperation methodstarts, the first internet TV box 71, the second internet TV box 72 andthe third internet TV box 73 can play the video programs according to avideo playlist, which is set by the cable TV setting staff 74.Consequently, the purpose of cooperatively implementing the networkplaying task will be achieved.

From the above descriptions, the networking cooperation method of thepresent invention has the following benefits. Since the participants forparticipating in the networking cooperation method can receive the URIthrough the corresponding platforms and/or channels and build thecooperative working environments (i.e., the projected relationalsynchronization workspaces), any identity (including any person or anymachine) can be invited to cooperatively implement the task without theneed of additionally installing an application software or anapplication program in the personal device (e.g., a computer). Secondly,since the working environment for allowing these cooperators tocooperatively implement the task can be unified into a unifiedenvironment by the unifying process, any information, any tool or anyservice can be arbitrarily combined together and compatible with eachother according to the operational demand of any cooperator. Thirdly,any information, any tool or any service in the cooperative workingenvironment (i.e., the projected relational synchronization workspace)can be operated by any cooperator. Moreover, since the cooperativeworking environments (i.e., the projected relational synchronizationworkspaces) for allowing these cooperators to cooperatively implementthe task are projected to and executed in the personal devices (e.g.,computers) of all cooperators, any cooperate can synchronously view thechange of the cooperative working environment in response to anoperation of other cooperator. Fourthly, in comparison with theconventional cooperation method of sharing the screen image, thenetworking cooperation method of the present invention allows thesynchronization command to be transferred between the projectedrelational synchronization workspaces in order to achieve thesynchronizing efficacy. Since the networking cooperation method of thepresent invention only transmits the synchronization command instead oftransmitting the data of the whole screen, the bandwidth usage islargely reduced and the network performance is effectively enhanced.

While the invention has been described in terms of what is presentlyconsidered to be the most practical and preferred embodiments, it is tobe understood that the invention needs not be limited to the disclosedembodiments. On the contrary, it is intended to cover variousmodifications and similar arrangements included within the spirit andscope of the appended claims which are to be accorded with the broadestinterpretation so as to encompass all such modifications and similarstructures.

What is claimed is:
 1. A networking cooperation method, comprising stepsof: combining a plurality of unified matters together into a projectablespace instance for modeling a relational synchronization workspaceaccording to an operational demand from at least one promoter; andprojecting the relational synchronization workspace to at least oneparticipant, wherein the projected relational synchronization workspaceequips the plurality of unified matters according to the projectablespace instance, wherein the at least one participant accesses theprojected relational synchronization workspace to cooperativelyimplement a task with the at least one promoter and/or at least oneother participant.
 2. The networking cooperation method according toclaim 1, wherein at least two of the at least one promoter, the at leastone participant and the at least one other participant are related witheach other according to the operational demand.
 3. The networkingcooperation method according to claim 1, wherein when at least one ofthe at least one promoter, the at least one participant and the otherparticipant performs at least one operation on the correspondingprojected relational synchronization workspace to result in a change ofthe corresponding projected relational synchronization workspace, theprojected relational synchronization workspace corresponding to at leastanother of the at least one promoter, the at least one participant andthe other participant is synchronously changed according to acorresponding synchronization setting.
 4. The networking cooperationmethod according to claim 3, wherein when the at least one of the atleast one promoter, the at least one participant and the otherparticipant performs the at least one operation on the correspondingprojected relational synchronization workspace, a synchronizationcommand is generated; and/or the synchronization command is transmittedto the corresponding projected relational synchronization workspace ofthe at least another of the at least one promoter, the at least oneparticipant and the other participant through a client-serverarchitecture or a peer-to-peer architecture, so that the projectedrelational synchronization workspaces of the at least one promoter, theat least one participant and the other participant are synchronouslychanged.
 5. The networking cooperation method according to claim 1,wherein the at least one participant includes a machine, and/or the atleast one other participant includes another machine.
 6. The networkingcooperation method according to claim 1, wherein an operating mode ofthe projected relational synchronization workspace includes a one userto one user mode, a one user to multiple user mode or a multiple user tomultiple user mode.
 7. The networking cooperation method according toclaim 1, wherein the plurality of unified matters added to theprojectable space instance include at least one matterizer, at least oneunified tool and/or at least one unified information unit, wherein theat least one unified tool and/or the at least one unified informationunit is imported into the corresponding projected relationalsynchronization workspace through the at least one matterizer.
 8. Thenetworking cooperation method according to claim 7, wherein each of theunified matters is produced after an original matter from at least oneinformation source is unified by the at least one matterizer, whereineach of the unified matters is added to the projectable space instance.9. The networking cooperation method according to claim 8, wherein atleast one original tool corresponding to the at least one unified toolincludes a utility, a widget, an agent, an application, a service or anyexecutable element accessible from a corresponding machine or a server,and/or at least one original information corresponding to the at leastone unified information unit includes a file, a web page, a databaserow, a policy, a rule, a policy of the relational synchronizationworkspace, or any information accessible from a corresponding machine ora server.
 10. The networking cooperation method according to claim 1,wherein the projecting step comprises sub-steps of: acquiring theprojectable space instance through a uniform resource identifier; andusing a projector to parse the projectable space instance to build aworking environment, so that the projected relational synchronizationworkspace is executed in the working environment.
 11. The networkingcooperation method according to claim 10, wherein the projector isloaded into an engine that provides a compatible environment to executethe projector.
 12. The networking cooperation method according to claim10, wherein the engine includes at least one of a Javascript engine, aWindows application or a Linux application.
 13. The networkingcooperation method according to claim 1, wherein the projectable spaceinstance is an object, an extensible markup language document, or aninstance which is instantiated with a structured language or astructured protocol.
 14. A networking cooperation method, comprisingsteps of: combining a plurality of unified matters together into aprojectable space instance for modeling a relational synchronizationworkspace according to an operational demand; and projecting therelational synchronization workspace to multiple cooperators, whereinthe projected relational synchronization workspace equips with theplurality of unified matters according to the projectable spaceinstance, wherein at least one cooperator of the multiple cooperatorsaccesses the projected relational synchronization workspace tocooperatively implement a task with at least one other cooperator of themultiple cooperators.
 15. The networking cooperation method according toclaim 14, wherein at least two of the multiple cooperators are relatedwith each other according to the operational demand.
 16. The networkingcooperation method according to claim 14, wherein when the at least onecooperator of the multiple cooperators performs at least one operationon the corresponding projected relational synchronization workspace toresult in a change of the corresponding projected relationalsynchronization workspace, the projected relational synchronizationworkspace corresponding to the at least one other cooperator of themultiple cooperators is synchronously changed according to acorresponding synchronization setting.
 17. The networking cooperationmethod according to claim 16, wherein when the at least one cooperatorof the multiple cooperators performs the at least one operation on thecorresponding projected relational synchronization workspace, asynchronization command is generated; and/or the synchronization commandis transmitted to the corresponding projected relational synchronizationworkspace of the at least one other cooperator of the multiplecooperators through a client-server architecture or a peer-to-peerarchitecture, so that the projected relational synchronizationworkspaces of the multiple cooperators are synchronously changed. 18.The networking cooperation method according to claim 14, wherein each ofthe multiple cooperators includes a machine.
 19. The networkingcooperation method according to claim 14, wherein an operating mode ofthe projected relational synchronization workspace includes a onecooperator to one cooperator mode, a one cooperator to multiplecooperator mode or a multiple cooperator to multiple cooperator mode.20. The networking cooperation method according to claim 14, wherein theplurality of unified matters added to the projectable space instanceinclude at least one matterizer, at least one unified tool and/or atleast one unified information unit, wherein the at least one unifiedtool and/or the at least one unified information unit is imported intothe corresponding projected relational synchronization workspace throughthe at least one matterizer.
 21. The networking cooperation methodaccording to claim 20, wherein each of the unified matters is producedafter an original matter from at least one information source is unifiedby the at least one matterizer, wherein each of the unified matters isadded to the projectable space instance.
 22. The networking cooperationmethod according to claim 14, wherein the projecting step comprisessub-steps of: acquiring the projectable space instance through a uniformresource identifier; and using a projector to parse the projectablespace instance to build a working environment, so that the projectedrelational synchronization workspace is executed in the workingenvironment.
 23. A machine comprising a projector, wherein after themachine receives a projectable space instance, the projector parses theprojectable space instance to build a projected relationalsynchronization workspace corresponding to the projectable spaceinstance, wherein after the projected relational synchronizationworkspace equips a plurality of unified matters that are combined in theprojectable space instance, the machine and at least one cooperatorcooperatively implement a task, or at least one cooperator of multiplecooperators accesses the projected relational synchronization workspaceand cooperate with at least one other cooperator of the multiplecooperators to cooperatively implement the task, wherein the pluralityof unified matters are combined together into the projectable spaceinstance according to an operational demand.
 24. The machine accordingto claim 23, wherein each of the multiple cooperators comprises an othermachine.
 25. The machine according to claim 23, wherein when the atleast one cooperator of the multiple cooperators performs at least oneoperation on the corresponding projected relational synchronizationworkspace to result in a change of the corresponding projectedrelational synchronization workspace, the projected relationalsynchronization workspace corresponding to the at least one othercooperator of the multiple cooperators is synchronously changedaccording to a corresponding synchronization setting.
 26. The machineaccording to claim 23, wherein the projected relational synchronizationworkspace corresponding to the at least one other cooperator of themultiple cooperators is built in at least one other machine.
 27. Themachine according to claim 23, wherein at least two of the multiplecooperators are related with each other according to the operationaldemand.
 28. The machine according to claim 23, wherein the plurality ofunified matters added to the projectable space instance include at leastone matterizer, at least one unified tool and/or at least one unifiedinformation unit, wherein the at least one unified tool and/or the atleast one unified information unit is imported into the correspondingprojected relational synchronization workspace through the at least onematterizer.
 29. The machine according to claim 28, wherein each of theunified matters is produced after an original matter from at least oneinformation source is unified by the at least one matterizer, whereineach of the unified matters is added to the projectable space instance.30. The machine according to claim 29, wherein at least one originaltool corresponding to the at least one unified tool includes a utility,a widget, an agent, an application, a service or any executable elementaccessible from a corresponding machine or a server, and/or at least oneoriginal information corresponding to the at least one unifiedinformation unit includes a file, a web page, a database row, a policy,a rule, a policy of the projected relational synchronization workspace,or any information accessible from a corresponding machine or a server.